Process execution directory structure

Runtime owners can create additional storage space for process executions.

In the default setup, process executions are stored in the \<atom_installation_directory>/execution/history/<execution_date> directory. If your total number of process executions is very high, you may reach certain operating-system driven limitations such as how many files you can store in a given folder. For that or other reasons, you may choose to set the container property com.boomi.container.executionDirNestLevel to sort your process executions into nested subdirectories derived from the execution ID. The value can be set from 0 to 4 nested directories with 0 as the default. The subdirectory limitation is determined by the operating system's file system limitations.

In this example, where the execution ID is execution-f1dbbb70-3053-4ca0-8179-fcb483fed7c0-2012.11.28, selecting a value of 0–4 creates the following subdirectory structure:

• 0 — (the default) execution/history/2012.11.28/execution-f1dbbb70-3053-4ca0-8179-fcb483fed7c0-2012.11.28

• 1 — execution/history/2012.11.28/f1/execution-f1dbbb70-3053-4ca0-8179-fcb483fed7c0-2012.11.28

• 2 — execution/history/2012.11.28/f1/db/execution-f1dbbb70-3053-4ca0-8179-fcb483fed7c0-2012.11.28

• 3 — execution/history/2012.11.28/f1/db/bb/execution-f1dbbb70-3053-4ca0-8179-fcb483fed7c0-2012.11.28

• 4 — execution/history/2012.11.28/f1/db/bb/70/execution-f1dbbb70-3053-4ca0-8179-fcb483fed7c0-2012.11.28

Selecting a higher number makes the subdirectory structure deeper with more available subdirectories to store process executions. A production runtime cloud, for example, typically has a container property value of 2.